home *** CD-ROM | disk | FTP | other *** search
- Path: sascha.esrac.ele.tue.nl!leon
- From: leon@esrac.ele.tue.nl (Leon Woestenberg)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: OS features
- Date: 10 Jan 1996 12:19:06 GMT
- Organization: Eindhoven Student Radio Amateur Club
- Message-ID: <4d0arq$gga@tuegate.tue.nl>
- References: <92747544038@PAPA.NORTH.DE> <4b3h9s$1st@alterdial.UU.NET> <2152.6561T63T2136@cycor.ca> <4b7i18$si1@vixen.cso.uiuc.edu> <oj6raxxrr0o.fsf@hpsrk.fc.hp.com> <13213431@sourcery.han.de>
- NNTP-Posting-Host: sascha.esrac.ele.tue.nl
- X-Newsreader: TIN [version 1.2 PL2]
-
- Olaf Barthel (olsen@sourcery.han.de) wrote:
- : This really calls for a different OS. One idea that has been brought
- : forward was to come up with a scheme that allows for different processes
- : to run in different memory spaces, very much like running multiple
- : AmigaOS sessions on the same machine. That way you can gun an environment
-
- This is one of the reason VM is used nowadays; VM allows the address
- mapping; one map for each process.
-
- : that has crashed and see the other environments survive. But there is a
- : problem to solve: how to implement shared memory accesses and interprocess
- : communication without running into the same trouble the original Amiga
- : shared memory space causes?
-
- By splitting the memory map for one process in private and shared memory.
- If process A and B have to share data, the shared data block can be mapped
- to the shared memory part of process A, and likewise for process B.
- Each memory block should have a list of allowed processes.
-
- Of course, there's the extra task switch overhead.
-
- : That's an idea. I have seen similar under BeOS which can put contiguous
- : memory regions together from fragments.
-
- This is a definity must for a VM model candidate. If the new AmigaOS isn't
- going to use VM for memory protection, it should at least be used to allow
- allocation of a large contiguous block of (virtual) memory.
-
- Leon Woestenberg.
-